Dynomotion

Group: DynoMotion Message: 3638 From: himykabibble Date: 1/31/2012
Subject: Happy, Happy! Joy, Joy!
Today I moved my app out to the machines PC for the first time, and I'm happy to report it performed flawlessly (well, within the limits of its current state of incompleteness). I didn't actually get to cut metal, due to an unexpected mechanical repair I had to perform on the machine, but I will certainly do so tomorrow. I did run several program cutting air, and all performed perfectly.

So, I am a VERY happy camper! Thanks again to Tom and Brad, who made this possible!

Now I have to learn more about building installers with VC2010. My app will not work if I simply publish it, and I imagine it's because VS2010 decides for itself WHERE to install it, and I think it's not finding the dotNet libraries. So, for now, I can only run it under VS2010. But, that's really a nit at this point.

Regards,
Ray L.
Group: DynoMotion Message: 3639 From: Brad Murry Date: 1/31/2012
Subject: Re: Happy, Happy! Joy, Joy!

Great news Ray,

 

You could just copy your files manually without an installer…

 

Express versions of VS do not allow for deployment products.

 

-Brad Murry

 

From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
Sent: Tuesday, January 31, 2012 3:52 PM
To: DynoMotion@yahoogroups.com
Subject: [DynoMotion] Happy, Happy! Joy, Joy!

 

 

Today I moved my app out to the machines PC for the first time, and I'm happy to report it performed flawlessly (well, within the limits of its current state of incompleteness). I didn't actually get to cut metal, due to an unexpected mechanical repair I had to perform on the machine, but I will certainly do so tomorrow. I did run several program cutting air, and all performed perfectly.

So, I am a VERY happy camper! Thanks again to Tom and Brad, who made this possible!

Now I have to learn more about building installers with VC2010. My app will not work if I simply publish it, and I imagine it's because VS2010 decides for itself WHERE to install it, and I think it's not finding the dotNet libraries. So, for now, I can only run it under VS2010. But, that's really a nit at this point.

Regards,
Ray L.

Group: DynoMotion Message: 3640 From: himykabibble Date: 1/31/2012
Subject: Re: Happy, Happy! Joy, Joy!
Brad,

That was the approach I tried first, but it didn't work. I copied my entire solution tree, and the entire KMotion tree from my laptop to my machines PC, and when I try to start the app it would just put up a blank white window, then hang. Any idea what's going on there? If I publish then install, it's not finding dotNet, and blows up when the app tries to create the KM_Controller.

I did figure out how to get the project into VS2008, even though when you try to open it directly, VS2008 refuses to open it, because the solution file version is different. But, if you just edit the version number in the solution file, it opens just fine. But, I can't get it to run in the debugger, because VS2008 apparently does not support .NET 4.0.

Are you using 2010 Pro?

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> Great news Ray,
>
>
>
> You could just copy your files manually without an installer.
>
>
>
> Express versions of VS do not allow for deployment products.
>
>
>
> -Brad Murry
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> Behalf Of himykabibble
> Sent: Tuesday, January 31, 2012 3:52 PM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Happy, Happy! Joy, Joy!
>
>
>
>
>
> Today I moved my app out to the machines PC for the first time, and I'm
> happy to report it performed flawlessly (well, within the limits of its
> current state of incompleteness). I didn't actually get to cut metal, due to
> an unexpected mechanical repair I had to perform on the machine, but I will
> certainly do so tomorrow. I did run several program cutting air, and all
> performed perfectly.
>
> So, I am a VERY happy camper! Thanks again to Tom and Brad, who made this
> possible!
>
> Now I have to learn more about building installers with VC2010. My app will
> not work if I simply publish it, and I imagine it's because VS2010 decides
> for itself WHERE to install it, and I think it's not finding the dotNet
> libraries. So, for now, I can only run it under VS2010. But, that's really a
> nit at this point.
>
> Regards,
> Ray L.
>